Batch Status and Locating Processed Transactions

You can see details about the batch job in the the Jumio Portal / Settings / Identity Verification / Batch Uploads page.

Status

Status Name Comment
CREATED Initial job creation
IN_PROGRESS Job execution initialize
IN_PROGRESS_INGEST Validating the input file, and ingest into database for process
IN_PROGRESS_PROCESS Create/upload credentials/finalize workflows base on data from ingest step
IN_PROGRESS_WAITING_PROCESSED_CONFIRMATION All workflows are created, uploaded with credentials and finalized, now waiting for PROCESSED message for each workflow
COMPLETED Job execution received target amount of workflow PROCESSED messages
ERROR An error is encountered in middle of a job execution. See Error Messages

Locating Processed Transactions

You can retrieve all processed transactions using the same Request Reference you see on the status page as a "filter" criteria within the "Reporting Criteria" field in Explorer page on Jumio Portal.

Batch transactions use the API Channel.

Error Messages

Download the job information to see error messages. The batch will check for errors in two phases:

  • At input validation

  • At the time of workflow creation

If an input file is invalid (for example if a required column is missing) no workflows will be executed. Fix the issue with the file and create a new batch job.

If the input is valid the transactions will be processed sequentially by the row number in the CSV. If a specific transaction causes the error the batch job will terminate, and the row number of the problematic transaction will be available in the job information. In this case, fix the issue with the transaction and create a new batch job, with all of the rows from the original input.csv from the fixed transaction down.

 

Error message example

 

 

Error Name Detail Present to User Can User Self - Repair Comment
INPUT_FILE_NOT_FOUND YES YES Either the input.csv is not found or an image file referenced within input.csv is not found.
INVALID_CSV YES YES

The CSV is invalid. This could be do to:

  • A string is too long

  • Not all headers and data present

  • Other reason that causes the csv to be invalid
INVALID_FILE_SIZE YES YES Either the input.csv exceeds the allowed file size, or one of images referenced within input.csv exceeds the allowed file size.
JUMIO_WORKFLOW_API NO NO/YES This is an internal error, due to the Jumio API not being able to complete the workflow process.
JUMIO_WORKFLOW_API_UNAUTHORIZED NO NO/YES The Jumio API rejected the workflow request with Unauthorized (401). The stored credential may no longer be valid or available, and may need to be updated.
JUMIO_WORKFLOW_API_FORBIDDEN NO NO/YES The Jumio API rejected the workflow request with Forbidden (403). The stored credential may not have the required permissions, and may need to be updated.
INGEST_ERROR NO NO This is due to some unexpected input validation error other than the ones listed above. Contact Support.
PROCESS_ERROR NO NO This is due to some unexpected processing error while reading the raw records and creating workflows from . Contact Support.
NO_AVAILABLE_EXECUTOR NO NO Contact Support.